Identification of conflict rules in a network intent formal equivalence failure

ABSTRACT

Systems, methods, and computer-readable media for identifying conflict rules between models of network intents. A first and second model of network intents are obtained, the models describing the operation and communication between one or more network devices in a network. A logical exclusive disjunction between the first and second models is calculated over the space of possible packet conditions and network actions defined by models, without enumerating all possible packet conditions and network actions. It is detected whether the models are in conflict with respect to at least a first network device. If the models are in conflict, it is determined whether a given rule of a plurality of rules associated with the first model is a conflict rule. The determining comprises calculating the intersection between the given rule and the logical exclusive disjunction, wherein the given rule is a conflict rule if the calculated intersection is non-zero.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 15/693,220 filed on Aug. 31, 2017, which claims the benefit of U.S. Provisional Patent Application Ser. No. 62/513,037 filed on May 31, 2017, the contents of which are incorporated by reference in their entireties.

TECHNICAL FIELD

The present technology pertains to network configuration and troubleshooting, and more specifically to the detection and identification of conflict rules that underlie a formal equivalence failure between models of network intents.

BACKGROUND

Computer networks are becoming increasingly complex, often involving low level as well as high level configurations at various layers of the network. For example, computer networks generally include numerous access policies, forwarding policies, routing policies, security policies, quality-of-service (QoS) policies, etc., which together define the overall behavior and operation of the network. Network operators have a wide array of configuration options for tailoring the network to the needs of the users. While the different configuration options available provide network operators a great degree of flexibility and control over the network, they also add to the complexity of the network. In many cases, the configuration process can become highly complex. Not surprisingly, the network configuration process is increasingly error prone. In addition, troubleshooting errors in a highly complex network can be extremely difficult. The process of identifying the root cause of undesired behavior in the network can be a daunting task.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which the above-recited and other advantages and features of the disclosure can be obtained, a more particular description of the principles briefly described above will be rendered by reference to specific embodiments thereof which are illustrated in the appended drawings. Understanding that these drawings depict only exemplary embodiments of the disclosure and are not therefore to be considered to be limiting of its scope, the principles herein are described and explained with additional specificity and detail through the use of the accompanying drawings in which:

FIGS. 1A and 1B illustrate example network environments;

FIG. 2A illustrates an example object model for a network;

FIG. 2B illustrates an example object model for a tenant object in the example object model from FIG. 2A;

FIG. 2C illustrates an example association of various objects in the example object model from FIG. 2A;

FIG. 2D illustrates a schematic diagram of example models for implementing the example object model from FIG. 2A;

FIG. 3A illustrates an example network assurance appliance;

FIG. 3B illustrates an example system for network assurance;

FIG. 3C illustrates a schematic diagram of an example system for static policy analysis in a network;

FIG. 4 illustrates an example method embodiment for network assurance and fault code aggregation;

FIG. 5 illustrates an example architecture for identification of conflict rules;

FIG. 6A illustrates an first example conflict Reduced Ordered Binary Decision Diagram (ROBDD);

FIG. 6B illustrates a second example conflict ROBDD;

FIG. 6C illustrates the example conflict ROBDD of FIG. 6B with the addition of a new rule;

FIG. 7 illustrates an example network device in accordance with various embodiments; and

FIG. 8 illustrates an example computing device in accordance with various embodiments.

DESCRIPTION OF EXAMPLE EMBODIMENTS

Various embodiments of the disclosure are discussed in detail below. While specific implementations are discussed, it should be understood that this is done for illustration purposes only. A person skilled in the relevant art will recognize that other components and configurations may be used without parting from the spirit and scope of the disclosure. Thus, the following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding of the disclosure. However, in certain instances, well-known or conventional details are not described in order to avoid obscuring the description. References to one or an embodiment in the present disclosure can be references to the same embodiment or any embodiment; and, such references mean at least one of the embodiments.

Reference to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others.

The terms used in this specification generally have their ordinary meanings in the art, within the context of the disclosure, and in the specific context where each term is used. Alternative language and synonyms may be used for any one or more of the terms discussed herein, and no special significance should be placed upon whether or not a term is elaborated or discussed herein. In some cases, synonyms for certain terms are provided. A recital of one or more synonyms does not exclude the use of other synonyms. The use of examples anywhere in this specification including examples of any terms discussed herein is illustrative only, and is not intended to further limit the scope and meaning of the disclosure or of any example term. Likewise, the disclosure is not limited to various embodiments given in this specification.

Without intent to limit the scope of the disclosure, examples of instruments, apparatus, methods and their related results according to the embodiments of the present disclosure are given below. Note that titles or subtitles may be used in the examples for convenience of a reader, which in no way should limit the scope of the disclosure. Unless otherwise defined, technical and scientific terms used herein have the meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. In the case of conflict, the present document, including definitions will control.

Additional features and advantages of the disclosure will be set forth in the description which follows, and in part will be obvious from the description, or can be learned by practice of the herein disclosed principles. The features and advantages of the disclosure can be realized and obtained by means of the instruments and combinations particularly pointed out in the appended claims. These and other features of the disclosure will become more fully apparent from the following description and appended claims, or can be learned by the practice of the principles set forth herein.

OVERVIEW

Disclosed herein are systems, methods, and computer-readable media for identifying specific conflict rules between two or more models of network intents that have failed a formal equivalence check or are otherwise not congruent (e.g. a software-defined logical intent is not rendered correctly into a switch as a corresponding hardware intent). In some examples, conflict rules might be identified from a one or more known failures of formal equivalence or congruency, and in some examples, conflict rules might be identified without an a priori knowledge of one or more failures of formal equivalence or congruency.

A logical model of network intents can be a model generated based on configurations defined in one or more controllers or servers in a software-defined network (SDN), such as an APIC (application policy infrastructure controller) in an ACI (application-centric infrastructure) network. The logical model can thus represent the logical configuration of the SDN network (e.g., a representation of the logical configurations in the ACI). The logical configuration of the SDN network can be based on the configurations defined by the network operator for the SDN network, such as the configurations entered into the APIC of an ACI network, and may thus reflect the intent of the network operator or the intended behavior of the SDN network.

A hardware model of network intents can be a model generated based on the logical model. The hardware model can thus represent the hardware rendering of the discrete software-defined components that comprise the logical model. Often times, there is not a one-to-one correspondence between a software-defined logical intent and a hardware-defined intent. For example, the hardware rendering of the logical model might cause a single logical intent to be broken into multiple different hardware intents. This is not problematic in and of itself, as long as the multiple hardware intents capture the exact same effect as the single logical intent. However, conventional network assurance processes struggle to make this determination of equivalency, as it requires a comparison of two models of network intents that do not have a congruent form. As such, it would be desirable to provide intelligent network assurance via systems and methods for identifying conflict rules between two or more models of network intents that are not necessarily congruent in form or in composition.

DESCRIPTION

The disclosed technology addresses the need in the art for a reliable and efficient ability to identify conflict rules or other equivalence failures between two or more models of network intents. The present technology involves systems, methods, and computer-readable media for receiving as input two or more models of network intents (which may or may not be known to have conflicts or equivalency failures) and subsequently generating a listing of one or more paired conflict rules that cause the models to conflict or otherwise fail an equivalency check. For example, a conflict rules pair might consist of two rules in a first model that conflict with one rule in a second model.

The present technology will be subsequently described as follows. The discussion begins with an introductory discussion of network assurance and a description of example computing environments, as illustrated in FIGS. 1A and 1B. The discussion continues with a description of systems and methods for network assurance, network modeling, and event generation, as shown in FIGS. 2A-2D, 3A-C, and 4. The discussion moves next to an example formal analysis architecture for identification of conflict rules as illustrated in FIG. 5, and several example ROBDDs as seen in FIGS. 6A-6C. The discussion then concludes with a description of an example network device, as illustrated in FIG. 7, and an example computing device, as illustrated in FIG. 8, including example hardware components suitable for hosting software applications and performing computing operations. The disclosure now turns to a discussion of network assurance, the analysis and execution of which is a precursor to the event generation in accordance with embodiments of the present disclosure.

Network assurance is the guarantee or determination that the network is behaving as intended by the network operator and has been configured properly (e.g., the network is doing what it is intended to do). Intent can encompass various network operations, such as bridging, routing, security, service chaining, endpoints, compliance, QoS (Quality of Service), audits, etc. Intent can be embodied in one or more policies, settings, configurations, etc., defined for the network and individual network elements (e.g., switches, routers, applications, resources, etc.). However, often times, the configurations, policies, etc., defined by a network operator are incorrect or not accurately reflected in the actual behavior of the network. For example, a network operator specifies a configuration A for one or more types of traffic but later finds out that the network is actually applying configuration B to that traffic or otherwise processing that traffic in a manner that is inconsistent with configuration A. This can be a result of many different causes, such as hardware errors, software bugs, varying priorities, configuration conflicts, misconfiguration of one or more settings, improper rule rendering by devices, unexpected errors or events, software upgrades, configuration changes, failures, etc. As another example, a network operator implements configuration C but one or more other configurations result in the network behaving in a manner that is inconsistent with the intent reflected by the implementation of configuration C. For example, such a situation can result when configuration C conflicts with other configurations in the network.

The approaches herein can provide network assurance by modeling various aspects of the network and/or performing consistency checks as well as other network assurance checks. The network assurance approaches herein can be implemented in various types of networks, including a private network, such as a local area network (LAN); an enterprise network; a standalone or traditional network, such as a data center network; a network including a physical or underlay layer and a logical or overlay layer, such as a VXLAN or software-defined network (SDN) (e.g., Application Centric Infrastructure (ACI) or VMware NSX networks); etc. The approaches herein can also enable identification and visualization of hardware-level (e.g., network switch-level) errors along any software or application-centric dimension. In this manner, data center operators can quickly see hardware errors that impact particular tenants or other logical entities, across the entire network fabric, and even drill down by other dimensions, such as endpoint groups, to see only those relevant hardware errors. These visualizations speed root cause analysis, improving data center and application availability metrics.

Logical models can be implemented to represent various aspects of a network. A model can include a mathematical or semantic model of the network, including, without limitation the network's policies, configurations, requirements, security, routing, topology, applications, hardware, filters, contracts, access control lists, EPGs, application profiles, tenants, etc. Models can be implemented to provide network assurance to ensure that the network is properly configured and the behavior of the network will be consistent (or is consistent) with the intended behavior reflected through specific policies, settings, definitions, etc., implemented by the network operator. Unlike traditional network monitoring which involves sending and analyzing data packets and observing network behavior, network assurance can be performed through modeling without necessarily ingesting any packet data or monitoring traffic or network behavior. This can result in foresight, insight, and hindsight: problems can be prevented before they occur, identified when they occur, and fixed immediately after they occur.

Properties of the network can be mathematically modeled to deterministically predict the behavior and condition of the network. A mathematical model can abstract the control, management, and data planes, and may use various techniques such as symbolic, formal verification, consistency, graph, behavioral, etc. The network can be determined to be healthy if the model(s) indicate proper behavior (e.g., no inconsistencies, conflicts, errors, etc.). The network can be determined to be functional, but not fully healthy, if the modeling indicates proper behavior but some inconsistencies. The network can be determined to be non-functional and not healthy if the modeling indicates improper behavior and errors. If inconsistencies or errors are detected by the modeling, a detailed analysis of the corresponding model(s) can allow one or more underlying or root problems to be identified with great accuracy.

The models can consume numerous types of data and/or events which model a large amount of behavioral aspects of the network. Such data and events can impact various aspects of the network, such as underlay services, overlay service, tenant connectivity, tenant security, tenant EP mobility, tenant policy, resources, etc.

Having described various aspects of network assurance and fault code aggregation across dimensions, the disclosure now turns to a discussion of example network environments for network assurance.

FIG. 1A illustrates a diagram of an example Network Environment 100, such as a data center. The Network Environment 100 can include a Fabric 120 which can represent the physical layer or infrastructure (e.g., underlay) of the Network Environment 100. Fabric 120 can include Spines 102 (e.g., spine routers or switches) and Leafs 104 (e.g., leaf routers or switches) which can be interconnected for routing or switching traffic in the Fabric 120. Spines 102 can interconnect Leafs 104 in the Fabric 120, and Leafs 104 can connect the Fabric 120 to an overlay or logical portion of the Network Environment 100, which can include application services, servers, virtual machines, containers, endpoints, etc. Thus, network connectivity in the Fabric 120 can flow from Spines 102 to Leafs 104, and vice versa. The interconnections between Leafs 104 and Spines 102 can be redundant (e.g., multiple interconnections) to avoid a failure in routing. In some embodiments, Leafs 104 and Spines 102 can be fully connected, such that any given Leaf is connected to each of the Spines 102, and any given Spine is connected to each of the Leafs 104. Leafs 104 can be, for example, top-of-rack (“ToR”) switches, aggregation switches, gateways, ingress and/or egress switches, provider edge devices, and/or any other type of routing or switching device.

Leafs 104 can be responsible for routing and/or bridging tenant or customer packets and applying network policies or rules. Network policies and rules can be driven by one or more Controllers 116, and/or implemented or enforced by one or more devices, such as Leafs 104. Leafs 104 can connect other elements to the Fabric 120. For example, Leafs 104 can connect Servers 106, Hypervisors 108, Virtual Machines (VMs) 110, Applications 112, Network Device 114, etc., with Fabric 120. Such elements can reside in one or more logical or virtual layers or networks, such as an overlay network. In some cases, Leafs 104 can encapsulate and decapsulate packets to and from such elements (e.g., Servers 106) in order to enable communications throughout Network Environment 100 and Fabric 120. Leafs 104 can also provide any other devices, services, tenants, or workloads with access to Fabric 120. In some cases, Servers 106 connected to Leafs 104 can similarly encapsulate and decapsulate packets to and from Leafs 104. For example, Servers 106 can include one or more virtual switches or routers or tunnel endpoints for tunneling packets between an overlay or logical layer hosted by, or connected to, Servers 106 and an underlay layer represented by Fabric 120 and accessed via Leafs 104.

Applications 112 can include software applications, services, containers, appliances, functions, service chains, etc. For example, Applications 112 can include a firewall, a database, a CDN server, an IDS/IPS, a deep packet inspection service, a message router, a virtual switch, etc. An application from Applications 112 can be distributed, chained, or hosted by multiple endpoints (e.g., Servers 106, VMs 110, etc.), or may run or execute entirely from a single endpoint.

VMs 110 can be virtual machines hosted by Hypervisors 108 or virtual machine managers running on Servers 106. VMs 110 can include workloads running on a guest operating system on a respective server. Hypervisors 108 can provide a layer of software, firmware, and/or hardware that creates, manages, and/or runs the VMs 110. Hypervisors 108 can allow VMs 110 to share hardware resources on Servers 106, and the hardware resources on Servers 106 to appear as multiple, separate hardware platforms. Moreover, Hypervisors 108 on Servers 106 can host one or more VMs 110.

In some cases, VMs 110 and/or Hypervisors 108 can be migrated to other Servers 106. Servers 106 can similarly be migrated to other locations in Network Environment 100. For example, a server connected to a specific leaf can be changed to connect to a different or additional leaf. Such configuration or deployment changes can involve modifications to settings, configurations and policies that are applied to the resources being migrated as well as other network components.

In some cases, one or more Servers 106, Hypervisors 108, and/or VMs 110 can represent or reside in a tenant or customer space. Tenant space can include workloads, services, applications, devices, networks, and/or resources that are associated with one or more clients or subscribers. Accordingly, traffic in Network Environment 100 can be routed based on specific tenant policies, spaces, agreements, configurations, etc. Moreover, addressing can vary between one or more tenants. In some configurations, tenant spaces can be divided into logical segments and/or networks and separated from logical segments and/or networks associated with other tenants. Addressing, policy, security and configuration information between tenants can be managed by Controllers 116, Servers 106, Leafs 104, etc.

Configurations in Network Environment 100 can be implemented at a logical level, a hardware level (e.g., physical), and/or both. For example, configurations can be implemented at a logical and/or hardware level based on endpoint or resource attributes, such as endpoint types and/or application groups or profiles, through a software-defined network (SDN) framework (e.g., Application-Centric Infrastructure (ACI) or VMWARE NSX). To illustrate, one or more administrators can define configurations at a logical level (e.g., application or software level) through Controllers 116, which can implement or propagate such configurations through Network Environment 100. In some examples, Controllers 116 can be Application Policy Infrastructure Controllers (APICs) in an ACI framework. In other examples, Controllers 116 can be one or more management components for associated with other SDN solutions, such as NSX Managers.

Such configurations can define rules, policies, priorities, protocols, attributes, objects, etc., for routing and/or classifying traffic in Network Environment 100. For example, such configurations can define attributes and objects for classifying and processing traffic based on Endpoint Groups (EPGs), Security Groups (SGs), VM types, bridge domains (BDs), virtual routing and forwarding instances (VRFs), tenants, priorities, firewall rules, etc. Other example network objects and configurations are further described below. Traffic policies and rules can be enforced based on tags, attributes, or other characteristics of the traffic, such as protocols associated with the traffic, EPGs associated with the traffic, SGs associated with the traffic, network address information associated with the traffic, etc. Such policies and rules can be enforced by one or more elements in Network Environment 100, such as Leafs 104, Servers 106, Hypervisors 108, Controllers 116, etc. As previously explained, Network Environment 100 can be configured according to one or more particular software-defined network (SDN) solutions, such as CISCO ACI or VMWARE NSX. These example SDN solutions are briefly described below.

ACI can provide an application-centric or policy-based solution through scalable distributed enforcement. ACI supports integration of physical and virtual environments under a declarative configuration model for networks, servers, services, security, requirements, etc. For example, the ACI framework implements EPGs, which can include a collection of endpoints or applications that share common configuration requirements, such as security, QoS, services, etc. Endpoints can be virtual/logical or physical devices, such as VMs, containers, hosts, or physical servers that are connected to Network Environment 100. Endpoints can have one or more attributes such as a VM name, guest OS name, a security tag, application profile, etc. Application configurations can be applied between EPGs, instead of endpoints directly, in the form of contracts. Leafs 104 can classify incoming traffic into different EPGs. The classification can be based on, for example, a network segment identifier such as a VLAN ID, VXLAN Network Identifier (VNID), NVGRE Virtual Subnet Identifier (VSID), MAC address, IP address, etc.

In some cases, classification in the ACI infrastructure can be implemented by Application Virtual Switches (AVS), which can run on a host, such as a server or switch. For example, an AVS can classify traffic based on specified attributes, and tag packets of different attribute EPGs with different identifiers, such as network segment identifiers (e.g., VLAN ID). Finally, Leafs 104 can tie packets with their attribute EPGs based on their identifiers and enforce policies, which can be implemented and/or managed by one or more Controllers 116. Leaf 104 can classify to which EPG the traffic from a host belongs and enforce policies accordingly.

Another example SDN solution is based on VMWARE NSX. With VMWARE NSX, hosts can run a distributed firewall (DFW) which can classify and process traffic. Consider a case where three types of VMs, namely, application, database and web VMs, are put into a single layer-2 network segment. Traffic protection can be provided within the network segment based on the VM type. For example, HTTP traffic can be permitted among web VMs, and not permitted between a web VM and an application or database VM. To classify traffic and implement policies, VMWARE NSX can implement security groups, which can be used to group the specific VMs (e.g., web VMs, application VMs, database VMs). DFW rules can be configured to implement policies for the specific security groups. To illustrate, in the context of the previous example, DFW rules can be configured to block HTTP traffic between web, application, and database security groups.

Returning now to FIG. 1A, Network Environment 100 can deploy different hosts via Leafs 104, Servers 106, Hypervisors 108, VMs 110, Applications 112, and Controllers 116, such as VMWARE ESXi hosts, WINDOWS HYPER-V hosts, bare metal physical hosts, etc. Network Environment 100 may interoperate with a variety of Hypervisors 108, Servers 106 (e.g., physical and/or virtual servers), SDN orchestration platforms, etc. Network Environment 100 may implement a declarative model to allow its integration with application design and holistic network policy.

Controllers 116 can provide centralized access to fabric information, application configuration, resource configuration, application-level configuration modeling for a software-defined network (SDN) infrastructure, integration with management systems or servers, etc. Controllers 116 can form a control plane that interfaces with an application plane via northbound APIs and a data plane via southbound APIs.

As previously noted, Controllers 116 can define and manage application-level model(s) for configurations in Network Environment 100. In some cases, application or device configurations can also be managed and/or defined by other components in the network. For example, a hypervisor or virtual appliance, such as a VM or container, can run a server or management tool to manage software and services in Network Environment 100, including configurations and settings for virtual appliances.

As illustrated above, Network Environment 100 can include one or more different types of SDN solutions, hosts, etc. For the sake of clarity and explanation purposes, various examples in the disclosure will be described with reference to an ACI framework, and Controllers 116 may be interchangeably referenced as controllers, APICs, or APIC controllers. However, it should be noted that the technologies and concepts herein are not limited to ACI solutions and may be implemented in other architectures and scenarios, including other SDN solutions as well as other types of networks which may not deploy an SDN solution.

Further, as referenced herein, the term “hosts” can refer to Servers 106 (e.g., physical or logical), Hypervisors 108, VMs 110, containers (e.g., Applications 112), etc., and can run or include any type of server or application solution. Non-limiting examples of “hosts” can include virtual switches or routers, such as distributed virtual switches (DVS), application virtual switches (AVS), vector packet processing (VPP) switches; VCENTER and NSX MANAGERS; bare metal physical hosts; HYPER-V hosts; VMs; DOCKER Containers; etc.

FIG. 1B illustrates another example of Network Environment 100. In this example, Network Environment 100 includes Endpoints 122 connected to Leafs 104 in Fabric 120. Endpoints 122 can be physical and/or logical or virtual entities, such as servers, clients, VMs, hypervisors, software containers, applications, resources, network devices, workloads, etc. For example, an Endpoint 122 can be an object that represents a physical device (e.g., server, client, switch, etc.), an application (e.g., web application, database application, etc.), a logical or virtual resource (e.g., a virtual switch, a virtual service appliance, a virtualized network function (VNF), a VM, a service chain, etc.), a container running a software resource (e.g., an application, an appliance, a VNF, a service chain, etc.), storage, a workload or workload engine, etc. Endpoints 122 can have an address (e.g., an identity), a location (e.g., host, network segment, virtual routing and forwarding (VRF) instance, domain, etc.), one or more attributes (e.g., name, type, version, patch level, OS name, OS type, etc.), a tag (e.g., security tag), a profile, etc.

Endpoints 122 can be associated with respective Logical Groups 118. Logical Groups 118 can be logical entities containing endpoints (physical and/or logical or virtual) grouped together according to one or more attributes, such as endpoint type (e.g., VM type, workload type, application type, etc.), one or more requirements (e.g., policy requirements, security requirements, QoS requirements, customer requirements, resource requirements, etc.), a resource name (e.g., VM name, application name, etc.), a profile, platform or operating system (OS) characteristics (e.g., OS type or name including guest and/or host OS, etc.), an associated network or tenant, one or more policies, a tag, etc. For example, a logical group can be an object representing a collection of endpoints grouped together. To illustrate, Logical Group 1 can contain client endpoints, Logical Group 2 can contain web server endpoints, Logical Group 3 can contain application server endpoints, Logical Group N can contain database server endpoints, etc. In some examples, Logical Groups 118 are EPGs in an ACI environment and/or other logical groups (e.g., SGs) in another SDN environment.

Traffic to and/or from Endpoints 122 can be classified, processed, managed, etc., based Logical Groups 118. For example, Logical Groups 118 can be used to classify traffic to or from Endpoints 122, apply policies to traffic to or from Endpoints 122, define relationships between Endpoints 122, define roles of Endpoints 122 (e.g., whether an endpoint consumes or provides a service, etc.), apply rules to traffic to or from Endpoints 122, apply filters or access control lists (ACLs) to traffic to or from Endpoints 122, define communication paths for traffic to or from Endpoints 122, enforce requirements associated with Endpoints 122, implement security and other configurations associated with Endpoints 122, etc.

In an ACI environment, Logical Groups 118 can be EPGs used to define contracts in the ACI. Contracts can include rules specifying what and how communications between EPGs take place. For example, a contract can define what provides a service, what consumes a service, and what policy objects are related to that consumption relationship. A contract can include a policy that defines the communication path and all related elements of a communication or relationship between endpoints or EPGs. For example, a Web EPG can provide a service that a Client EPG consumes, and that consumption can be subject to a filter (ACL) and a service graph that includes one or more services, such as firewall inspection services and server load balancing.

FIG. 2A illustrates a diagram of an example Management Information Model 200 for an SDN network, such as Network Environment 100. The following discussion of Management Information Model 200 references various terms which shall also be used throughout the disclosure. Accordingly, for clarity, the disclosure shall first provide below a list of terminology, which will be followed by a more detailed discussion of Management Information Model 200.

As used herein, the terms “Aliasing” and “Shadowing” can refer to a rule (e.g., contracts, policies, configurations, etc.) that overlaps one or more other rules. For example, Contract 1 defined in a logical model of a network can be said to be aliasing or shadowing Contract 2 defined in the logical model of the network if Contract 1 overlaps Contract 2. In this example, by aliasing or shadowing Contract 2, Contract 1 may render Contract 2 redundant or inoperable. For example, if Contract 1 has a higher priority than Contract 2, such aliasing can render Contract 2 redundant based on Contract 1's overlapping and higher priority characteristics.

As used herein, the term “APIC” can refer to one or more controllers (e.g., Controllers 116) in an ACI framework. The APIC can provide a unified point of automation and management, policy programming, application deployment, health monitoring for an ACI multitenant fabric. The APIC can be implemented as a single controller, a distributed controller, or a replicated, synchronized, and/or clustered controller.

As used herein, the term “BDD” can refer to a binary decision tree. A binary decision tree can be a data structure representing functions, such as Boolean functions.

As used herein, the term “BD” can refer to a bridge domain. A bridge domain can be a set of logical ports that share the same flooding or broadcast characteristics. Like a virtual LAN (VLAN), bridge domains can span multiple devices. A bridge domain can be a L2 (Layer 2) construct.

As used herein, a “Consumer” can refer to an endpoint, resource, and/or EPG that consumes a service.

As used herein, a “Context” can refer to an L3 (Layer 3) address domain that permits multiple instances of a routing table to exist and work simultaneously. This increases functionality by permitting network paths to be segmented without using multiple devices. Non-limiting examples of a context or L3 address domain can include a Virtual Routing and Forwarding (VRF) instance, a private network, and so forth.

As used herein, the term “Contract” can refer to rules or configurations that specify what and how communications in a network are conducted (e.g., permitted, denied, filtered, processed, etc.). In an ACI network, contracts can specify how communications between endpoints and/or EPGs take place. In some examples, a contract can provide rules and configurations akin to an Access Control List (ACL).

As used herein, the term “Distinguished Name” (DN) can refer to a unique name that describes an object, such as an MO, and locates its place in Management Information Model 200. In some cases, the DN can be (or equate to) a Fully Qualified Domain Name (FQDN).

As used herein, the term “Endpoint Group” (EPG) can refer to a logical entity or object associated with a collection or group of endoints as previously described with reference to FIG. 1B.

As used herein, the term “Filter” can refer to a parameter or configuration for permitting communications. For example, in a whitelist model where all communications are blocked by default, a communication must be given explicit permission to prevent such communication from being blocked. A filter can define permission(s) for one or more communications or packets. A filter can thus function similar to an ACL or Firewall rule. In some examples, a filter can be implemented in a packet (e.g., TCP/IP) header field, such as L3 protocol type, L4 (Layer 4) ports, and so on, which is used to permit inbound or outbound communications between endpoints or EPGs, for example.

As used herein, the term “L2 Out” can refer to a bridged connection. A bridged connection can connect two or more segments of the same network so that they can communicate. In an ACI framework, an L2 out can be a bridged (Layer 2) connection between an ACI fabric (e.g., Fabric 120) and an outside Layer 2 network, such as a switch.

As used herein, the term “L3 Out” can refer to a routed connection. A routed Layer 3 connection uses a set of protocols that determine the path that data follows in order to travel across networks from its source to its destination. Routed connections can perform forwarding (e.g., IP forwarding) according to a protocol selected, such as BGP (border gateway protocol), OSPF (Open Shortest Path First), EIGRP (Enhanced Interior Gateway Routing Protocol), etc.

As used herein, the term “Managed Object” (MO) can refer to an abstract representation of objects that are managed in a network (e.g., Network Environment 100). The objects can be concrete objects (e.g., a switch, server, adapter, etc.), or logical objects (e.g., an application profile, an EPG, a fault, etc.). The MOs can be network resources or elements that are managed in the network. For example, in an ACI environment, an MO can include an abstraction of an ACI fabric (e.g., Fabric 120) resource.

As used herein, the term “Management Information Tree” (MIT) can refer to a hierarchical management information tree containing the MOs of a system. For example, in ACI, the MIT contains the MOs of the ACI fabric (e.g., Fabric 120). The MIT can also be referred to as a Management Information Model (MIM), such as Management Information Model 200.

As used herein, the term “Policy” can refer to one or more specifications for controlling some aspect of system or network behavior. For example, a policy can include a named entity that contains specifications for controlling some aspect of system behavior. To illustrate, a Layer 3 Outside Network Policy can contain the BGP protocol to enable BGP routing functions when connecting Fabric 120 to an outside Layer 3 network.

As used herein, the term “Profile” can refer to the configuration details associated with a policy. For example, a profile can include a named entity that contains the configuration details for implementing one or more instances of a policy. To illustrate, a switch node profile for a routing policy can contain the switch-specific configuration details to implement the BGP routing protocol.

As used herein, the term “Provider” refers to an object or entity providing a service. For example, a provider can be an EPG that provides a service.

As used herein, the term “Subject” refers to one or more parameters in a contract for defining communications. For example, in ACI, subjects in a contract can specify what information can be communicated and how. Subjects can function similar to ACLs.

As used herein, the term “Tenant” refers to a unit of isolation in a network. For example, a tenant can be a secure and exclusive virtual computing environment. In ACI, a tenant can be a unit of isolation from a policy perspective, but does not necessarily represent a private network. Indeed, ACI tenants can contain multiple private networks (e.g., VRFs). Tenants can represent a customer in a service provider setting, an organization or domain in an enterprise setting, or just a grouping of policies.

As used herein, the term “VRF” refers to a virtual routing and forwarding instance. The VRF can define a Layer 3 address domain that permits multiple instances of a routing table to exist and work simultaneously. This increases functionality by permitting network paths to be segmented without using multiple devices. Also known as a context or private network.

Having described various terms used herein, the disclosure now returns to a discussion of Management Information Model (MIM) 200 in FIG. 2A. As previously noted, MIM 200 can be a hierarchical management information tree or MIT. Moreover, MIM 200 can be managed and processed by Controllers 116, such as APICs in an ACI. Controllers 116 can enable the control of managed resources by presenting their manageable characteristics as object properties that can be inherited according to the location of the object within the hierarchical structure of the model.

The hierarchical structure of MIM 200 starts with Policy Universe 202 at the top (Root) and contains parent and child nodes 116, 204, 206, 208, 210, 212. Nodes 116, 202, 204, 206, 208, 210, 212 in the tree represent the managed objects (MOs) or groups of objects. Each object in the fabric (e.g., Fabric 120) has a unique distinguished name (DN) that describes the object and locates its place in the tree. The Nodes 116, 202, 204, 206, 208, 210, 212 can include the various MOs, as described below, which contain policies that govern the operation of the system.

Controllers 116

Controllers 116 (e.g., APIC controllers) can provide management, policy programming, application deployment, and health monitoring for Fabric 120.

Node 204

Node 204 includes a tenant container for policies that enable an administrator to exercise domain-based access control. Non-limiting examples of tenants can include:

User tenants defined by the administrator according to the needs of users. They contain policies that govern the operation of resources such as applications, databases, web servers, network-attached storage, virtual machines, and so on.

The common tenant is provided by the system but can be configured by the administrator. It contains policies that govern the operation of resources accessible to all tenants, such as firewalls, load balancers, Layer 4 to Layer 7 services, intrusion detection appliances, and so on.

The infrastructure tenant is provided by the system but can be configured by the administrator. It contains policies that govern the operation of infrastructure resources such as the fabric overlay (e.g., VXLAN). It also enables a fabric provider to selectively deploy resources to one or more user tenants. Infrastructure tenant polices can be configurable by the administrator.

The management tenant is provided by the system but can be configured by the administrator. It contains policies that govern the operation of fabric management functions used for in-band and out-of-band configuration of fabric nodes. The management tenant contains a private out-of-bound address space for the Controller/Fabric internal communications that is outside the fabric data path that provides access through the management port of the switches. The management tenant enables discovery and automation of communications with virtual machine controllers.

Node 206

Node 206 can contain access policies that govern the operation of switch access ports that provide connectivity to resources such as storage, compute, Layer 2 and Layer 3 (bridged and routed) connectivity, virtual machine hypervisors, Layer 4 to Layer 7 devices, and so on. If a tenant requires interface configurations other than those provided in the default link, Cisco Discovery Protocol (CDP), Link Layer Discovery Protocol (LLDP), Link Aggregation Control Protocol (LACP), or Spanning Tree Protocol (STP), an administrator can configure access policies to enable such configurations on the access ports of Leafs 104.

Node 206 can contain fabric policies that govern the operation of the switch fabric ports, including such functions as Network Time Protocol (NTP) server synchronization, Intermediate System-to-Intermediate System Protocol (IS-IS), Border Gateway Protocol (BGP) route reflectors, Domain Name System (DNS) and so on. The fabric MO contains objects such as power supplies, fans, chassis, and so on.

Node 208

Node 208 can contain VM domains that group VM controllers with similar networking policy requirements. VM controllers can share virtual space (e.g., VLAN or VXLAN space) and application EPGs. Controllers 116 communicate with the VM controller to publish network configurations such as port groups that are then applied to the virtual workloads.

Node 210

Node 210 can contain Layer 4 to Layer 7 service integration life cycle automation framework that enables the system to dynamically respond when a service comes online or goes offline. Policies can provide service device package and inventory management functions.

Node 212

Node 212 can contain access, authentication, and accounting (AAA) policies that govern user privileges, roles, and security domains of Fabric 120.

The hierarchical policy model can fit well with an API, such as a REST API interface. When invoked, the API can read from or write to objects in the MIT. URLs can map directly into distinguished names that identify objects in the MIT. Data in the MIT can be described as a self-contained structured tree text document encoded in XML or JSON, for example.

FIG. 2B illustrates an example object model 220 for a tenant portion of MIM 200. As previously noted, a tenant is a logical container for application policies that enable an administrator to exercise domain-based access control. A tenant thus represents a unit of isolation from a policy perspective, but it does not necessarily represent a private network. Tenants can represent a customer in a service provider setting, an organization or domain in an enterprise setting, or just a convenient grouping of policies. Moreover, tenants can be isolated from one another or can share resources.

Tenant portion 204A of MIM 200 can include various entities, and the entities in Tenant Portion 204A can inherit policies from parent entities. Non-limiting examples of entities in Tenant Portion 204A can include Filters 240, Contracts 236, Outside Networks 222, Bridge Domains 230, VRF Instances 234, and Application Profiles 224.

Bridge Domains 230 can include Subnets 232. Contracts 236 can include Subjects 238. Application Profiles 224 can contain one or more EPGs 226. Some applications can contain multiple components. For example, an e-commerce application could require a web server, a database server, data located in a storage area network, and access to outside resources that enable financial transactions. Application Profile 224 contains as many (or as few) EPGs as necessary that are logically related to providing the capabilities of an application.

EPG 226 can be organized in various ways, such as based on the application they provide, the function they provide (such as infrastructure), where they are in the structure of the data center (such as DMZ), or whatever organizing principle that a fabric or tenant administrator chooses to use.

EPGs in the fabric can contain various types of EPGs, such as application EPGs, Layer 2 external outside network instance EPGs, Layer 3 external outside network instance EPGs, management EPGs for out-of-band or in-band access, etc. EPGs 226 can also contain Attributes 228, such as encapsulation-based EPGs, IP-based EPGs, or MAC-based EPGs.

As previously mentioned, EPGs can contain endpoints (e.g., EPs 122) that have common characteristics or attributes, such as common policy requirements (e.g., security, virtual machine mobility (VMM), QoS, or Layer 4 to Layer 7 services). Rather than configure and manage endpoints individually, they can be placed in an EPG and managed as a group.

Policies apply to EPGs, including the endpoints they contain. An EPG can be statically configured by an administrator in Controllers 116, or dynamically configured by an automated system such as VCENTER or OPENSTACK.

To activate tenant policies in Tenant Portion 204A, fabric access policies should be configured and associated with tenant policies. Access policies enable an administrator to configure other network configurations, such as port channels and virtual port channels, protocols such as LLDP, CDP, or LACP, and features such as monitoring or diagnostics.

FIG. 2C illustrates an example Association 260 of tenant entities and access entities in MIM 200. Policy Universe 202 contains Tenant Portion 204A and Access Portion 206A. Thus, Tenant Portion 204A and Access Portion 206A are associated through Policy Universe 202.

Access Portion 206A can contain fabric and infrastructure access policies. Typically, in a policy model, EPGs are coupled with VLANs. For traffic to flow, an EPG is deployed on a leaf port with a VLAN in a physical, VMM, L2 out, L3 out, or Fiber Channel domain, for example.

Access Portion 206A thus contains Domain Profile 236 which can define a physical, VMM, L2 out, L3 out, or Fiber Channel domain, for example, to be associated to the EPGs. Domain Profile 236 contains VLAN Instance Profile 238 (e.g., VLAN pool) and Attacheable Access Entity Profile (AEP) 240, which are associated directly with application EPGs. The AEP 240 deploys the associated application EPGs to the ports to which it is attached, and automates the task of assigning VLANs. While a large data center can have thousands of active VMs provisioned on hundreds of VLANs, Fabric 120 can automatically assign VLAN IDs from VLAN pools. This saves time compared with trunking down VLANs in a traditional data center.

FIG. 2D illustrates a schematic diagram of example models for a network, such as Network Environment 100. The models can be generated based on specific configurations and/or network state parameters associated with various objects, policies, properties, and elements defined in MIM 200. The models can be implemented for network analysis and assurance, and may provide a depiction of the network at various stages of implementation and levels of the network.

As illustrated, the models can include L_Model 270A (Logical Model), LR_Model 270B (Logical Rendered Model or Logical Runtime Model), Li_Model 272 (Logical Model for i), Ci_Model 274 (Concrete model for i), and/or Hi_Model 276 (Hardware model or TCAM Model for i).

L_Model 270A is the logical representation of various elements in MIM 200 as configured in a network (e.g., Network Environment 100), such as objects, object properties, object relationships, and other elements in MIM 200 as configured in a network. L_Model 270A can be generated by Controllers 116 based on configurations entered in Controllers 116 for the network, and thus represents the logical configuration of the network at Controllers 116. This is the declaration of the “end-state” expression that is desired when the elements of the network entities (e.g., applications, tenants, etc.) are connected and Fabric 120 is provisioned by Controllers 116. Because L_Model 270A represents the configurations entered in Controllers 116, including the objects and relationships in MIM 200, it can also reflect the “intent” of the administrator: how the administrator wants the network and network elements to behave.

L_Model 270A can be a fabric or network-wide logical model. For example, L_Model 270A can account configurations and objects from each of Controllers 116. As previously explained, Network Environment 100 can include multiple Controllers 116. In some cases, two or more Controllers 116 may include different configurations or logical models for the network. In such cases, L_Model 270A can obtain any of the configurations or logical models from Controllers 116 and generate a fabric or network wide logical model based on the configurations and logical models from all Controllers 116. L_Model 270A can thus incorporate configurations or logical models between Controllers 116 to provide a comprehensive logical model. L_Model 270A can also address or account for any dependencies, redundancies, conflicts, etc., that may result from the configurations or logical models at the different Controllers 116.

LR_Model 270B is the abstract model expression that Controllers 116 (e.g., APICs in ACI) resolve from L_Model 270A. LR_Model 270B can provide the configuration components that would be delivered to the physical infrastructure (e.g., Fabric 120) to execute one or more policies. For example, LR_Model 270B can be delivered to Leafs 104 in Fabric 120 to configure Leafs 104 for communication with attached Endpoints 122. LR_Model 270B can also incorporate state information to capture a runtime state of the network (e.g., Fabric 120).

In some cases, LR_Model 270B can provide a representation of L_Model 270A that is normalized according to a specific format or expression that can be propagated to, and/or understood by, the physical infrastructure of Fabric 120 (e.g., Leafs 104, Spines 102, etc.). For example, LR_Model 270B can associate the elements in L_Model 270A with specific identifiers or tags that can be interpreted and/or compiled by the switches in Fabric 120, such as hardware plane identifiers used as classifiers.

Li_Model 272 is a switch-level or switch-specific model obtained from L_Model 270A and/or LR_Model 270B. Li_Model 272 can project L_Model 270A and/or LR_Model 270B on a specific switch or device i, and thus can convey how L_Model 270A and/or LR_Model 270B should appear or be implemented at the specific switch or device i.

For example, Li_Model 272 can project L_Model 270A and/or LR_Model 270B pertaining to a specific switch i to capture a switch-level representation of L_Model 270A and/or LR_Model 270B at switch i. To illustrate, Li_Model 272 L₁ can represent L_Model 270A and/or LR_Model 270B projected to, or implemented at, Leaf 1 (104). Thus, Li_Model 272 can be generated from L_Model 270A and/or LR_Model 270B for individual devices (e.g., Leafs 104, Spines 102, etc.) on Fabric 120.

In some cases, Li_Model 272 can be represented using JSON (JavaScript Object Notation). For example, Li_Model 272 can include JSON objects, such as Rules, Filters, Entries, and Scopes.

Ci_Model 274 is the actual in-state configuration at the individual fabric member i (e.g., switch i). In other words, Ci_Model 274 is a switch-level or switch-specific model that is based on Li_Model 272. For example, Controllers 116 can deliver Li_Model 272 to Leaf 1 (104). Leaf 1 (104) can take Li_Model 272, which can be specific to Leaf 1 (104), and render the policies in Li_Model 272 into a concrete model, Ci_Model 274, that runs on Leaf 1 (104). Leaf 1 (104) can render Li_Model 272 via the OS on Leaf 1 (104), for example. Thus, Ci_Model 274 can be analogous to compiled software, as it is the form of Li_Model 272 that the switch OS at Leaf 1 (104) can execute.

In some cases, Li_Model 272 and Ci_Model 274 can have a same or similar format. For example, Li_Model 272 and Ci_Model 274 can be based on JSON objects. Having the same or similar format can facilitate objects in Li_Model 272 and Ci_Model 274 to be compared for equivalence or congruence. Such equivalence or congruence checks can be used for network analysis and assurance, as further described herein.

Hi_Model 276 is also a switch-level or switch-specific model for switch i, but is based on Ci_Model 274 for switch i. Hi_Model 276 is the actual configuration (e.g., rules) stored or rendered on the hardware or memory (e.g., TCAM memory) at the individual fabric member i (e.g., switch i). For example, Hi_Model 276 can represent the configurations (e.g., rules) which Leaf 1 (104) stores or renders on the hardware (e.g., TCAM memory) of Leaf 1 (104) based on Ci_Model 274 at Leaf 1 (104). The switch OS at Leaf 1 (104) can render or execute Ci_Model 274, and Leaf 1 (104) can store or render the configurations from Ci_Model 274 in storage, such as the memory or TCAM at Leaf 1 (104). The configurations from Hi_Model 276 stored or rendered by Leaf 1 (104) represent the configurations that will be implemented by Leaf 1 (104) when processing traffic.

While Models 272, 274, 276 are shown as device-specific models, similar models can be generated or aggregated for a collection of fabric members (e.g., Leafs 104 and/or Spines 102) in Fabric 120. When combined, device-specific models, such as Model 272, Model 274, and/or Model 276, can provide a representation of Fabric 120 that extends beyond a particular device. For example, in some cases, Li_Model 272, Ci_Model 274, and/or Hi_Model 276 associated with some or all individual fabric members (e.g., Leafs 104 and Spines 102) can be combined or aggregated to generate one or more aggregated models based on the individual fabric members.

As referenced herein, the terms H Model, T Model, and TCAM Model can be used interchangeably to refer to a hardware model, such as Hi_Model 276. For example, Ti Model, Hi Model and TCAMi Model may be used interchangeably to refer to Hi_Model 276.

Models 270A, 270B, 272, 274, 276 can provide representations of various aspects of the network or various configuration stages for MIM 200. For example, one or more of Models 270A, 270B, 272, 274, 276 can be used to generate Underlay Model 278 representing one or more aspects of Fabric 120 (e.g., underlay topology, routing, etc.), Overlay Model 280 representing one or more aspects of the overlay or logical segment(s) of Network Environment 100 (e.g., COOP, MPBGP, tenants, VRFs, VLANs, VXLANs, virtual applications, VMs, hypervisors, virtual switching, etc.), Tenant Model 282 representing one or more aspects of Tenant portion 204A in MIM 200 (e.g., security, forwarding, service chaining, QoS, VRFs, BDs, Contracts, Filters, EPGs, subnets, etc.), Resources Model 284 representing one or more resources in Network Environment 100 (e.g., storage, computing, VMs, port channels, physical elements, etc.), etc.

In general, L_Model 270A can be the high-level expression of what exists in the LR_Model 270B, which should be present on the concrete devices as Ci_Model 274 and Hi_Model 276 expression. If there is any gap between the models, there may be inconsistent configurations or problems.

FIG. 3A illustrates a diagram of an example Assurance Appliance 300 for network assurance. In this example, Assurance Appliance 300 can include k VMs 110 operating in cluster mode. VMs are used in this example for explanation purposes. However, it should be understood that other configurations are also contemplated herein, such as use of containers, bare metal devices, Endpoints 122, or any other physical or logical systems. Moreover, while FIG. 3A illustrates a cluster mode configuration, other configurations are also contemplated herein, such as a single mode configuration (e.g., single VM, container, or server) or a service chain for example.

Assurance Appliance 300 can run on one or more Servers 106, VMs 110, Hypervisors 108, EPs 122, Leafs 104, Controllers 116, or any other system or resource. For example, Assurance Appliance 300 can be a logical service or application running on one or more VMs 110 in Network Environment 100.

The Assurance Appliance 300 can include Data Framework 308, which can be based on, for example, APACHE APEX and HADOOP. In some cases, assurance checks can be written as individual operators that reside in Data Framework 308. This enables a natively horizontal scale-out architecture that can scale to arbitrary number of switches in Fabric 120 (e.g., ACI fabric).

Assurance Appliance 300 can poll Fabric 120 at a configurable periodicity (e.g., an epoch). The analysis workflow can be setup as a DAG (Directed Acyclic Graph) of Operators 310, where data flows from one operator to another and eventually results are generated and persisted to Database 302 for each interval (e.g., each epoch).

The north-tier implements API Server (e.g., APACHE Tomcat and Spring framework) 304 and Web Server 306. A graphical user interface (GUI) interacts via the APIs exposed to the customer. These APIs can also be used by the customer to collect data from Assurance Appliance 300 for further integration into other tools.

Operators 310 in Data Framework 308 (e.g., APEX/Hadoop) can together support assurance operations. Below are non-limiting examples of assurance operations that can be performed by Assurance Appliance 300 via Operators 310.

Security Policy Adherence

Assurance Appliance 300 can check to make sure the configurations or specification from L_Model 270A, which may reflect the user's intent for the network, including for example the security policies and customer-configured contracts, are correctly implemented and/or rendered in Li_Model 272, Ci_Model 274, and Hi_Model 276, and thus properly implemented and rendered by the fabric members (e.g., Leafs 104), and report any errors, contract violations, or irregularities found.

Static Policy Analysis

Assurance Appliance 300 can check for issues in the specification of the user's intent or intents (e.g., identify contradictory or conflicting policies in L_Model 270A).

TCAM Utilization

TCAM is a scarce resource in the fabric (e.g., Fabric 120). However, Assurance Appliance 300 can analyze the TCAM utilization by the network data (e.g., Longest Prefix Match (LPM) tables, routing tables, VLAN tables, BGP updates, etc.), Contracts, Logical Groups 118 (e.g., EPGs), Tenants, Spines 102, Leafs 104, and other dimensions in Network Environment 100 and/or objects in MIM 200, to provide a network operator or user visibility into the utilization of this scarce resource. This can greatly help for planning and other optimization purposes.

Endpoint Checks

Assurance Appliance 300 can validate that the fabric (e.g. fabric 120) has no inconsistencies in the Endpoint information registered (e.g., two leafs announcing the same endpoint, duplicate subnets, etc.), among other such checks.

Tenant Routing Checks

Assurance Appliance 300 can validate that BDs, VRFs, subnets (both internal and external), VLANs, contracts, filters, applications, EPGs, etc., are correctly programmed.

Infrastructure Routing

Assurance Appliance 300 can validate that infrastructure routing (e.g., IS-IS protocol) has no convergence issues leading to black holes, loops, flaps, and other problems.

MP-BGP Route Reflection Checks

The network fabric (e.g., Fabric 120) can interface with other external networks and provide connectivity to them via one or more protocols, such as Border Gateway Protocol (BGP), Open Shortest Path First (OSPF), etc. The learned routes are advertised within the network fabric via, for example, MP-BGP. These checks can ensure that a route reflection service via, for example, MP-BGP (e.g., from Border Leaf) does not have health issues.

Logical Lint and Real-Time Change Analysis

Assurance Appliance 300 can validate rules in the specification of the network (e.g., L_Model 270A) are complete and do not have inconsistencies or other problems. MOs in the MIM 200 can be checked by Assurance Appliance 300 through syntactic and semantic checks performed on L_Model 270A and/or the associated configurations of the MOs in MIM 200. Assurance Appliance 300 can also verify that unnecessary, stale, unused or redundant configurations, such as contracts, are removed.

FIG. 3B illustrates an architectural diagram of an example system 350 for network assurance, such as Assurance Appliance 300. In some cases, system 350 can correspond to the DAG of Operators 310 previously discussed with respect to FIG. 3A

In this example, Topology Explorer 312 communicates with Controllers 116 (e.g., APIC controllers) in order to discover or otherwise construct a comprehensive topological view of Fabric 120 (e.g., Spines 102, Leafs 104, Controllers 116, Endpoints 122, and any other components as well as their interconnections). While various architectural components are represented in a singular, boxed fashion, it is understood that a given architectural component, such as Topology Explorer 312, can correspond to one or more individual Operators 310 and may include one or more nodes or endpoints, such as one or more servers, VMs, containers, applications, service functions (e.g., functions in a service chain or virtualized network function), etc.

Topology Explorer 312 is configured to discover nodes in Fabric 120, such as Controllers 116, Leafs 104, Spines 102, etc. Topology Explorer 312 can additionally detect a majority election performed amongst Controllers 116, and determine whether a quorum exists amongst Controllers 116. If no quorum or majority exists, Topology Explorer 312 can trigger an event and alert a user that a configuration or other error exists amongst Controllers 116 that is preventing a quorum or majority from being reached. Topology Explorer 312 can detect Leafs 104 and Spines 102 that are part of Fabric 120 and publish their corresponding out-of-band management network addresses (e.g., IP addresses) to downstream services. This can be part of the topological view that is published to the downstream services at the conclusion of Topology Explorer's 312 discovery epoch (e.g., 5 minutes, or some other specified interval).

In some examples, Topology Explorer 312 can receive as input a list of Controllers 116 (e.g., APIC controllers) that are associated with the network/fabric (e.g., Fabric 120). Topology Explorer 312 can also receive corresponding credentials to login to each controller. Topology Explorer 312 can retrieve information from each controller using, for example, REST calls. Topology Explorer 312 can obtain from each controller a list of nodes (e.g., Leafs 104 and Spines 102), and their associated properties, that the controller is aware of Topology Explorer 312 can obtain node information from Controllers 116 including, without limitation, an IP address, a node identifier, a node name, a node domain, a node URI, a node dm, a node role, a node version, etc.

Topology Explorer 312 can also determine if Controllers 116 are in quorum, or are sufficiently communicatively coupled amongst themselves. For example, if there are n controllers, a quorum condition might be met when (n/2+1) controllers are aware of each other and/or are communicatively coupled. Topology Explorer 312 can make the determination of a quorum (or identify any failed nodes or controllers) by parsing the data returned from the controllers, and identifying communicative couplings between their constituent nodes. Topology Explorer 312 can identify the type of each node in the network, e.g. spine, leaf, APIC, etc., and include this information in the topology information generated (e.g., topology map or model).

If no quorum is present, Topology Explorer 312 can trigger an event and alert a user that reconfiguration or suitable attention is required. If a quorum is present, Topology Explorer 312 can compile the network topology information into a JSON object and pass it downstream to other operators or services, such as Unified Collector 314.

Unified Collector 314 can receive the topological view or model from Topology Explorer 312 and use the topology information to collect information for network assurance from Fabric 120. Unified Collector 314 can poll nodes (e.g., Controllers 116, Leafs 104, Spines 102, etc.) in Fabric 120 to collect information from the nodes.

Unified Collector 314 can include one or more collectors (e.g., collector devices, operators, applications, VMs, etc.) configured to collect information from Topology Explorer 312 and/or nodes in Fabric 120. For example, Unified Collector 314 can include a cluster of collectors, and each of the collectors can be assigned to a subset of nodes within the topological model and/or Fabric 120 in order to collect information from their assigned subset of nodes. For performance, Unified Collector 314 can run in a parallel, multi-threaded fashion.

Unified Collector 314 can perform load balancing across individual collectors in order to streamline the efficiency of the overall collection process. Load balancing can be optimized by managing the distribution of subsets of nodes to collectors, for example by randomly hashing nodes to collectors.

In some cases, Assurance Appliance 300 can run multiple instances of Unified Collector 314. This can also allow Assurance Appliance 300 to distribute the task of collecting data for each node in the topology (e.g., Fabric 120 including Spines 102, Leafs 104, Controllers 116, etc.) via sharding and/or load balancing, and map collection tasks and/or nodes to a particular instance of Unified Collector 314 with data collection across nodes being performed in parallel by various instances of Unified Collector 314. Within a given node, commands and data collection can be executed serially. Assurance Appliance 300 can control the number of threads used by each instance of Unified Collector 314 to poll data from Fabric 120.

Unified Collector 314 can collect models (e.g., L_Model 270A and/or LR_Model 270B) from Controllers 116, switch software configurations and models (e.g., Ci_Model 274) from nodes (e.g., Leafs 104 and/or Spines 102) in Fabric 120, hardware configurations and models (e.g., Hi_Model 276) from nodes (e.g., Leafs 104 and/or Spines 102) in Fabric 120, etc. Unified Collector 314 can collect Ci_Model 274 and Hi_Model 276 from individual nodes or fabric members, such as Leafs 104 and Spines 102, and L_Model 270A and/or LR_Model 270B from one or more controllers (e.g., Controllers 116) in Network Environment 100.

Unified Collector 314 can poll the devices that Topology Explorer 312 discovers in order to collect data from Fabric 120 (e.g., from the constituent members of the fabric). Unified Collector 314 can collect the data using interfaces exposed by Controllers 116 and/or switch software (e.g., switch OS), including, for example, a Representation State Transfer (REST) Interface and a Secure Shell (SSH) Interface.

In some cases, Unified Collector 314 collects L_Model 270A, LR_Model 270B, and/or Ci_Model 274 via a REST API, and the hardware information (e.g., configurations, tables, fabric card information, rules, routes, etc.) via SSH using utilities provided by the switch software, such as virtual shell (VSH or VSHELL) for accessing the switch command-line interface (CLI) or VSH_LC shell for accessing runtime state of the line card.

Unified Collector 314 can poll other information from Controllers 116, including, without limitation: topology information, tenant forwarding/routing information, tenant security policies, contracts, interface policies, physical domain or VMM domain information, OOB (out-of-band) management IP's of nodes in the fabric, etc.

Unified Collector 314 can also poll information from nodes (e.g., Leafs 104 and Spines 102) in Fabric 120, including without limitation: Ci_Models 274 for VLANs, BDs, and security policies; Link Layer Discovery Protocol (LLDP) connectivity information of nodes (e.g., Leafs 104 and/or Spines 102); endpoint information from EPM/COOP; fabric card information from Spines 102; routing information base (RIB) tables from nodes in Fabric 120; forwarding information base (FIB) tables from nodes in Fabric 120; security group hardware tables (e.g., TCAM tables) from nodes in Fabric 120; etc.

In some cases, Unified Collector 314 can obtain runtime state from the network and incorporate runtime state information into L_Model 270A and/or LR_Model 270B. Unified Collector 314 can also obtain multiple logical models from Controllers 116 and generate a comprehensive or network-wide logical model (e.g., L_Model 270A and/or LR_Model 270B) based on the logical models. Unified Collector 314 can compare logical models from Controllers 116, resolve dependencies, remove redundancies, etc., and generate a single L_Model 270A and/or LR_Model 270B for the entire network or fabric.

Unified Collector 314 can collect the entire network state across Controllers 116 and fabric nodes or members (e.g., Leafs 104 and/or Spines 102). For example, Unified Collector 314 can use a REST interface and an SSH interface to collect the network state. This information collected by Unified Collector 314 can include data relating to the link layer, VLANs, BDs, VRFs, security policies, etc. The state information can be represented in LR_Model 270B, as previously mentioned. Unified Collector 314 can then publish the collected information and models to any downstream operators that are interested in or require such information. Unified Collector 314 can publish information as it is received, such that data is streamed to the downstream operators.

Data collected by Unified Collector 314 can be compressed and sent to downstream services. In some examples, Unified Collector 314 can collect data in an online fashion or real-time fashion, and send the data downstream, as it is collected, for further analysis. In some examples, Unified Collector 314 can collect data in an offline fashion, and compile the data for later analysis or transmission.

Assurance Appliance 300 can contact Controllers 116, Spines 102, Leafs 104, and other nodes to collect various types of data. In some scenarios, Assurance Appliance 300 may experience a failure (e.g., connectivity problem, hardware or software error, etc.) that prevents it from being able to collect data for a period of time. Assurance Appliance 300 can handle such failures seamlessly, and generate events based on such failures.

Switch Logical Policy Generator 316 can receive L_Model 270A and/or LR_Model 270B from Unified Collector 314 and calculate Li_Model 272 for each network device i (e.g., switch i) in Fabric 120. For example, Switch Logical Policy Generator 316 can receive L_Model 270A and/or LR_Model 270B and generate Li_Model 272 by projecting a logical model for each individual node i (e.g., Spines 102 and/or Leafs 104) in Fabric 120. Switch Logical Policy Generator 316 can generate Li_Model 272 for each switch in Fabric 120, thus creating a switch logical model based on L_Model 270A and/or LR_Model 270B for each switch.

Each Li_Model 272 can represent L_Model 270A and/or LR_Model 270B as projected or applied at the respective network device i (e.g., switch i) in Fabric 120. In some cases, Li_Model 272 can be normalized or formatted in a manner that is compatible with the respective network device. For example, Li_Model 272 can be formatted in a manner that can be read or executed by the respective network device. To illustrate, Li_Model 272 can included specific identifiers (e.g., hardware plane identifiers used by Controllers 116 as classifiers, etc.) or tags (e.g., policy group tags) that can be interpreted by the respective network device. In some cases, Li_Model 272 can include JSON objects. For example, Li_Model 272 can include JSON objects to represent rules, filters, entries, scopes, etc.

The format used for Li_Model 272 can be the same as, or consistent with, the format of Ci_Model 274. For example, both Li_Model 272 and Ci_Model 274 may be based on JSON objects. Similar or matching formats can enable Li_Model 272 and Ci_Model 274 to be compared for equivalence or congruence. Such equivalency checks can aid in network analysis and assurance as further explained herein.

Switch Logical Policy Generator 316 can also perform change analysis and generate lint events or records for problems discovered in L_Model 270A and/or LR_Model 270B. The lint events or records can be used to generate alerts for a user or network operator via an event generator coupled to receive lint events from Switch Logical Policy Generator 316.

Policy Operator 318 can receive Ci_Model 274 and Hi_Model 276 for each switch from Unified Collector 314, and Li_Model 272 for each switch from Switch Logical Policy Generator 316, and perform assurance checks and analysis (e.g., security adherence checks, TCAM utilization analysis, etc.) based on Ci_Model 274, Hi_Model 276, and Li_Model 272. Policy Operator 318 can perform assurance checks on a switch-by-switch basis by comparing one or more of the models. The output of Policy Operator 318 can be passed to an event generator (not shown) that can generate warning events for external consumption, where the events correspond to security violations or utilization statistics (such as TCAM usage) that comprise a policy violation. Such events are triggered by an abnormal or undesirable network occurrence as determined by the network generator, whereas a notification event might be triggered during the normal course of performing utilization analysis and security adherence checks in the absence of any violations.

Returning to Unified Collector 314, Unified Collector 314 can also send L_Model 270A and/or LR_Model 270B to Routing Policy Parser 320 (for L models), and Ci_Model 274 and Hi_Model 276 to Routing Parser 326 (for C and H models). Routing Policy Parser 320 can receive L_Model 270A and/or LR_Model 270B and parse the model(s) for information that may be relevant to downstream operators, such as Endpoint Checker 322 and Tenant Routing Checker 324. Similarly, Routing Parser 326 can receive Ci_Model 274 and Hi_Model 276 and parse each model for information for downstream operators, Endpoint Checker 322 and Tenant Routing Checker 324.

After Ci_Model 274, Hi_Model 276, L_Model 270A and/or LR_Model 270B are parsed, Routing Policy Parser 320 and/or Routing Parser 326 can send cleaned-up protocol buffers (Proto Buffs) to the downstream operators Endpoint Checker 322 and Tenant Routing Checker 324. Endpoint Checker 322 can communicate information related to Endpoint violations, such as duplicate IPs, APIPA, etc. to an event generator capable of generating events for external consumption or monitoring. Similarly, Tenant Routing Checker 324 can communicate information related to the deployment of BDs, VRFs, subnets, routing table prefixes, etc. to the same or different event generator capable of generating events for external consumption or monitoring.

FIG. 3C illustrates a schematic diagram of an example system for static policy analysis in a network (e.g., Network Environment 100). Static Policy Analyzer 360 can perform assurance checks to detect configuration violations, logical lint events, contradictory or conflicting policies, unused contracts, incomplete configurations, etc. Static Policy Analyzer 360 can check the specification of the user's intent or intents in L_Model 270A to determine if any configurations in Controllers 116 are inconsistent with the specification of the user's intent or intents.

Static Policy Analyzer 360 can include one or more of the Operators 310 executed or hosted in Assurance Appliance 300. However, in other configurations, Static Policy Analyzer 360 can run one or more operators or engines that are separate from Operators 310 and/or Assurance Appliance 300. For example, Static Policy Analyzer 360 can be a VM, a cluster of VMs, or a collection of endpoints in a service function chain.

Static Policy Analyzer 360 can receive as input L_Model 270A from Logical Model Collection Process 366 and Rules 368 defined for each feature (e.g., object) in L_Model 270A. Rules 368 can be based on objects, relationships, definitions, configurations, and any other features in MIM 200. Rules 368 can specify conditions, relationships, parameters, and/or any other information for identifying configuration violations or issues.

Moreover, Rules 368 can include information for identifying syntactic violations or issues. For example, Rules 368 can include one or more rules for performing syntactic checks. Syntactic checks can verify that the configuration of L_Model 270A is complete, and can help identify configurations or rules that are not being used. Syntactic checks can also verify that the configurations in the hierarchical MIM 200 are complete (have been defined) and identify any configurations that are defined but not used. To illustrate, Rules 368 can specify that every tenant in L_Model 270A should have a context configured; every contract in L_Model 270A should specify a provider EPG and a consumer EPG; every contract in L_Model 270A should specify a subject, filter, and/or port; etc.

Rules 368 can also include rules for performing semantic checks and identifying semantic violations or issues. Semantic checks can check conflicting rules or configurations. For example, Rule1 and Rule2 can have shadowing issues, Rule1 can be more specific than Rule2 and thereby create conflicts/issues, etc. Rules 368 can define conditions which may result in shadowed rules, conflicting rules, etc. To illustrate, Rules 368 can specify that a permit policy for a specific communication between two objects can conflict with a deny policy for the same communication between two objects if the permit policy has a higher priority than the deny policy, or a rule for an object renders another rule unnecessary.

Static Policy Analyzer 360 can apply Rules 368 to L_Model 270A to check configurations in L_Model 270A and output Configuration Violation Events 370 (e.g., alerts, logs, notifications, etc.) based on any issues detected. Configuration Violation Events 370 can include semantic or semantic problems, such as incomplete configurations, conflicting configurations, aliased/shadowed rules, unused configurations, errors, policy violations, misconfigured objects, incomplete configurations, incorrect contract scopes, improper object relationships, etc.

In some cases, Static Policy Analyzer 360 can iteratively traverse each node in a tree generated based on L_Model 270A and/or MIM 200, and apply Rules 368 at each node in the tree to determine if any nodes yield a violation (e.g., incomplete configuration, improper configuration, unused configuration, etc.). Static Policy Analyzer 360 can output Configuration Violation Events 370 when it detects any violations.

FIG. 4 illustrates an example flowchart for a network assurance model. At step 400, the method involves data collection. Data collection can include collection of data for operator intent, such as fabric data (e.g., topology, switch, interface policies, application policies, endpoint groups, etc.), network policies (e.g., BDs, VRFs, L2Outs, L3Outs, protocol configurations, etc.), security policies (e.g., contracts, filters, etc.), service chaining policies, and so forth. Data collection can also include data for the concrete, hardware model, such as network configuration (e.g., RIB/FIB, VLAN, MAC, ISIS, DB, BGP, OSPF, ARP, VPC, LLDP, MTU, QoS, etc.), security policies (e.g., TCAM, ECMP tables, etc.), endpoint dynamics (e.g., EPM, COOP EP DB, etc.), statistics (e.g., TCAM rule hits, interface counters, bandwidth, etc.).

At step 402, the method can involve formal modeling and analysis. Formal modeling and analysis can involve determining equivalency between logical and hardware models, such as security policies between models, etc.

At step 404, the method can involve smart event generation. Smart events can be generated using deep object hierarchy for detailed analysis, such as: Tenant, Leaf, VRFs, Rules; Filters, Routes, Prefixes, Port Numbers.

At step 406, the method can involve visualization. Formal models can be used to identify problems for analysis and debugging, in a user-friendly GUI.

Each of the previously described models (Li, Ci, and Hi) is, in one way or another, derived from the initial L-model that is configured by a user or network operator at the APIC or network controllers. For example, the Li model is a logical projection of the fabric-wide L model onto each leaf, spine, switch, node, etc. i in the network fabric; the Ci model is a concrete rendering of the L-model into a format that is compatible with the aforementioned fabric elements; and the Hi model is the hardware representation of the Ci model, as stored into switch memory by a switch memory controller.

Accordingly, each transformation used to derive the Li, Ci, and Hi models presents an opportunity for error or misconfiguration, which is undesirable from a network operator's point of view. These errors can result due to software bugs, user error, hardware variance, memory errors, overflow issues, and other causes that would be appreciated by one of ordinary skill in the art. In some embodiments, each model may consist of thousands, or tens of thousands, of distinct rules that collectively represent the intents configured in the original L-model, and each of these distinct rules must be preserved when converting between the different models.

Previous approaches to validating the Li, Ci, and Hi models relied upon brute force, treating each model as a black box and simply comparing the outputs from the models when given the same input. Such an approach can indicate a lack of equivalence if two models produce a different output for the same given input, but cannot provide any insight as to why there is a conflict. In particular, the black box approach is unable to provide specific information regarding the specific rules in each model that are in conflict, or specific information regarding the specific contract or intent configured by a user or network operator that ultimately led to the conflict arising.

Rather than employing brute force to determine the equivalence of two input models of network intents, the network intent models can instead be represented as Reduced Ordered Binary Decision Diagrams (ROBDDs), where each ROBDD is canonical (unique) to the input rules and their priority ordering. Each network intent model is first converted to a flat list of priority ordered rules (e.g. contracts defined by a customer or network operator are defined between EPGs, and rules are the specific node-to-node implementation of these contracts). In the example architecture 500 for a formal analysis engine 502 depicted in FIG. 5, flat lists of priority ordered rules for a plurality of models of network intents 506 (illustrated here are the models Li, Hi, and Ci) are received as input at an ROBDD generator 530 of a formal analysis engine 502. These rules can be represented as Boolean functions, where each rule consists of an action (e.g. Permit, Permit_Log, Deny, Deny_Log) and a set of conditions that will trigger that action (e.g. various configurations of packet source, destination, port, header, etc.). For example, a simple rule might be designed as Permit all traffic on port 80. In some embodiments, each rule might be a 147 bit string, with 13 fields of key-value pairs.

As a simplified example, consider a flat list of the priority ordered rules L1, L2, L3, and L4, where L1 is the highest priority rule and L4 is the lowest priority rule. A given packet is first checked against rule L1. If L1 is triggered, then the packet is handled according to the action contained in rule L1. Otherwise, the packet is then checked against rule L2. If L2 is triggered, then the packet is handled according to the action contained in rule L2. Otherwise, the packet is then checked against rule L3, and so on, until the packet either triggers a rule or reaches the end of the listing of rules.

The ROBDD Generator 530 can calculate one or more ROBDDs for the constituent rules L1-L4 of the model Li, or for the constituent rules of any other received model of network intents. In particular, an ROBDD can be generated for each action encoded by the rules L1-L4, or each action that might possibly be encoded by the rules L1-L4, such that there is a one-to-one correspondence between the number of actions and the number of ROBDDs generated. For example, the rules L1-L4 might be used to generate L_Permit_(BDD), L_Permit_Log_(BDD), L_Deny-_(BDD), and L_Deny_Log_(BDD). It is noted that within these ROBDDs, rules can be represented in their full (i.e. original) form, represented in a priority reduced form, or both. The full form is simply the form in which the rules were originally entered or created, and includes any overlaps or redundancies between separate rules. A priority reduced form removes the redundancies and overlaps, based on a given priority or hierarchical ordering of the rules. In this sense, a given rule has only a single full form, but can have numerous different priority reduced forms, depending on the priority listing that was used for the overall set of rules to which the given rule belongs.

When rules are represented in their priority reduced form, only the unique contribution of a given rule in light of all higher priority rules is considered. For the set of rules L1, L2, L3, L4, this priority reduced form would be given by L1, L1 ‘L2, (L1+L2)′L3, (L1+L2+L3)′L4, wherein L1’ denotes the inverse of L1, (L1+L2)′ denotes the inverse of the combination of L1 and L2, and so on. In this fashion, the rules considered in the semantic analysis described herein can in fact be priority reduced rules rather than full rules. For the same set of rules, but with the priority order L4, L3, L2, L1, the priority reduced form would be given by L4, L4′L3, (L4+L3)′L2, (L4+L3+L2)′L1. Thus, while in every case priority reduced rules remove any redundancies or overlaps between the conditions and actions encompassed by the rule sets, the priority order relies upon matters. Consequently, it can be advantageous for each ROBDD representation discussed herein to include both full and reduced representations. While reduced representations are more computationally efficient to work with, and reduced representations are the primary form of rule utilized in the analysis described herein, various different priority orderings are often needed, and thus it is helpful to maintain the full base representation from which priority reduced representations can be generated as needed.

Generally, ROBDD Generator 530 begins its calculation of a priority reduced form with the highest priority rule of the input listing of rules that is received. Continuing the example of rules L1-L4 of model Li, ROBDD Generator 530 begins with rule L1. Based on the action specified by rule L1 (e.g. Permit, Permit_Log, Deny, Deny_Log), rule L1 is added to the corresponding ROBDD for that action. Next, rule L2 will be added to the corresponding ROBDD for the action that it specifies. In some embodiments, a reduced form of L2 will be used, given by L1 ‘L2, with L1’ denoting the inverse of L1. This process is then repeated for rules L3 and L4, which have reduced forms given by (L1+L2)′L3 and (L1+L2+L3)′L4, respectively.

Notably, L_Permit_(BDD) and each of the other action-specific, priority reduced ROBDDs only encode the portion of each constituent rule L1, L2, L3, L4 that is not already captured by higher priority rules. That is, L1′L2 represents the portion of rule L2 that does not overlap with rule L1, (L1+L2)′L3 represents the portion of rule L3 that does not overlap with either rules L1 or L2, and (L1+L2+L3)′L4 represents the portion of rule L4 that does not overlap with either rules L1 or L2 or L3. This reduced form is independent of the action specified by an overlapping or higher priority rule and can be calculated based only on the conditions that will cause the higher priority rules to trigger. The use of these reduced forms can be particularly useful from a computational efficiency standpoint, as will be further explained below with reference to the calculation of conflict rules. As a general example, this improvement can be seen in the following example. Consider the case in which the priority ordered listing of rules L1, L2, L3, L4 has both L1 and L2 as conflict rules, and also has L1=L2. In other words, the two rules are redundant, and only one of them need appear in the conflict rules listing. Rather than performing such a redundancy check after the conflict rules calculation, such redundancy is instead avoided altogether by the use of a priority ordered listing of the reduced form of each rule. Because L1 and L2 are identical, the reduced form of L2 (i.e. L1′L2) is zero, and L2 does not appear in the priority ordered listing of reduced forms. In general, it is understood that the following description referring to various rules L_(i) can refer to either full rules or priority reduced rules without departing from the scope of the present disclosure.

ROBDD Generator 530 likewise can generate an ROBDD for each associated action of the remaining input models Ci and Hi, or any other models of network intents that are received at ROBDD Generator 530, with each ROBDD encoding one or more of the full base representation of the rules and one or more priority reduced forms of the constituent rules of the input model. From these ROBDDs, the formal equivalence of any two or more ROBDDs of network intent models can be checked via Equivalence Checker 540, which builds a conflict ROBDD encoding the areas of conflict between input ROBDDs.

Most typically, the ROBDDs being compared will be associated with the same action. For example, Equivalence Checker 540 can check the formal equivalence of L_Permit_(BDD) against H_Permit_(BDD) by calculating the exclusive disjunction between L_Permit_(BDD) and H_Permit_(BDD) More particularly, L_Permit_(BDD) ⊕ H_Permit_(BDD) (i.e. L_Permit_(BDD) XOR H_Permit_(BDD)) is calculated, although it is understood that the description below is equally applicable to all models of network intents (Li, Hi, Ci, etc.) and all associated actions (Permit, Permit_Log, Deny, Deny_Log, etc.).

An example calculation is illustrated in FIG. 6A, which portrays a heavily simplified representation of a Permit conflict ROBDD 600 a calculated for L_Permit_(BDD) and H_Permit_(BDD). As illustrated, L_Permit_(BDD) includes a unique portion 602 (shaded) and an overlap 604 (unshaded). Similarly, H_Permit_(BDD) includes a unique portion 606 (shaded) and the same overlap 604.

The Permit conflict ROBDD 600 a consists of unique portion 602, which represents the set of packet configurations and network actions that are encompassed within L_Permit_(BDD) but not H_Permit_(BDD) (i.e. calculated as L_Permit_(BDD)*H_Permit_(BDD)′), and unique portion 606, which represents the set of packet configurations and network actions that are encompassed within H_Permit_(BDD) but not L_Permit_(BDD) (i.e. calculated as L_Permit_(BDD)′ *H_Permit_(BDD)). Note that the unshaded overlap 604 is not part of Permit conflict ROBDD 600 a.

Conceptually, the full circle illustrating L_Permit_(BDD) (e.g. unique portion 602 and overlap 604) represents the fully enumerated set of packet configurations that are encompassed within, or trigger, the Permit rules encoded by the input model Li of logical network intents. For example, if Li contains the priority ordered reduced form rules:

L1: port=[1-3] Permit

L2: port=4 Permit

L3: port=[6-8] Permit

L4: port=9 Deny

where ‘port’ represents the port number of a received packet, then the circle illustrating L_Permit_(BDD) contains the set of all packets with port=[1-3], 4, [6-8] that are permitted. Everything outside of this full circle represents the space of packet conditions and/or actions that are different from those specified by the Permit rules contained in Li. For example, rule L4 encodes port=9 Deny and would fall outside of the region carved out by L_Permit_(BDD).

Similarly, the full circle illustrating H_Permit_(BDD) (e.g. unique portion 606 and overlap 604) represents the fully enumerated set of packet configurations and network actions that are encompassed within, or trigger, the Permit rules encoded by the input model Hi of hardware rendered network intents. Imagine that Hi contains the priority ordered reduced form rules:

H1: port=[1-3] Permit

H2: port=5 Permit

H3: port=[6-8] Deny

H4: port=10 Deny_Log

In the comparison between L_Permit_(BDD) and H_Permit_(BDD), only rules L1 and H1 are equivalent, because they match on both packet condition and action. L2 and H2 are not equivalent because even though they specify the same action (Permit), this action is triggered on a different port number (4 vs. 5). L3 and H3 are not equivalent because even though they trigger on the same port number (6-8), they trigger different actions (Permit vs. Deny). L4 and H4 are not equivalent because they trigger on a different port number (9 vs. 10) and also trigger different actions (Deny vs. Deny_Log). As such, overlap 604 contains only the set of packets that are captured by Permit rules L1 and H1, i.e. the packets with port=[1-3] that are permitted. Unique portion 602 contains only the set of packets that are captured by the Permit rules L2 and L3, while unique portion 606 contains only the set of packets that are captured by Permit rule H2. These two unique portions encode conflicts between the packet conditions upon which the logical Li model will trigger a Permit, and the packet conditions upon which the hardware rendered Hi model will trigger a Permit. Consequently, it is these two unique portions 602 and 606 that comprise Permit conflict ROBDD 600 a. The remaining rules L4, H3, and H4 are not Permit rules and consequently are not represented in L_Permit_(BDD), H_Permit_(BDD), or Permit conflict ROBDD 600 a.

In general, the action-specific overlaps between any two models of network intents contain only the set of packets that will trigger the same action no matter whether the rules of the first model or the rules of the second model are applied, while the action-specific conflict ROBDDs between these same two models contains the set of packets that result in conflicts by way of triggering on a different condition, triggering a different action, or both.

For purposes of clarity in the discussion above, Permit conflict ROBDD 600 a portrays L_Permit_(BDD) and H_Permit_(BDD) as singular entities rather than illustrating the effect of each individual priority reduced rule. Accordingly, FIGS. 6B and 6C present Permit conflict ROBDDs with individual priority reduced rules depicted. FIG. 6B presents a Permit conflict ROBDD 600 b taken between the illustrated listing of priority ordered reduced form rules L1, L2, H1, and H2. FIG. 6C presents a Permit conflict ROBDD 600 c that adds rule H3 to Permit conflict ROBDD 600 b. Both Figures maintain the same shading convention introduced in FIG. 6A, wherein a given conflict ROBDD comprises only the shaded regions that are shown.

Turning first to FIG. 6B, illustrated is a Permit conflict ROBDD 600 b that is calculated across a second L_Permit_(BDD) consisting of the priority ordered reduced form rules L1 and L2, and a second H_Permit_(BDD) consisting of the priority ordered reduced form rules H1 and H2. As illustrated, rules L1 and H1 are identical, and entirely overlap with one another—both rules consists of the overlap 612. For purposes of subsequent explanation, assume that rules L1 and H1 are both defined by port=[1-13] Permit. In general, note that the term ‘overlap’ is only applied between different models—because the reduced form of rules removes any overlap within a model itself, the term ‘overlap’ is not applied between constituent rules of the same model.

Continuing, it can be seen that the reduced rules L2 and H2 are not identical. Rule L2 consists of unique portion 614 and overlap 616. Rule H2 consists only of overlap 616, as it is contained entirely within the region encompassed by rule L2. For example, the reduced form of rule L2 might be port=[14-20] Permit, whereas rule H2 might be port=[15-17] Permit. Note that the use of this reduced form removes any overlap that might exist between rule L1 and L2, and between rule H1 and H2, such that the respective reduced forms consist only of the unique contributions of rules L2 and H2 in view of the respective higher priority rules.

As seen in FIG. 6B, a conflict exists between the Permit actions encoded by reduced rule L2 and the Permit actions encoded by reduced rule H2. Upon initial examination, it is possible that reduced rule L2 is overspecified, reduced rule H2 is underspecified, or some other combination. Conceptually, this is an example of an error that might be encountered by a network assurance check, wherein an Li-model rule (i.e. L2) specified by a user intent was incorrectly rendered into TCAM or switch memory as an Hi-model rule (i.e. H2). In particular, the scope of the rendered Hi-model rule H2 is smaller than the intended scope specified by the user intent contained in L2. For example, such a scenario could arise if a switch TCAM runs out of space, and does not have enough free entries to accommodate a full representation of an Li-model rule.

Regardless of the cause, this error is detected by the construction of the Permit conflict ROBDD 600 b as L_Permit_(BDD) ⊕H_Permit_(BDD) (⊕ indicates the logical exclusive disjunction, XOR), where the results of this calculation are indicated by the shaded unique portion 614. This unique portion 614 represents the set of packet configurations and network actions that are contained within L_Permit_(BDD) but not H_Permit_(BDD). In particular, unique portion 614 is contained within the region encompassed by reduced rule L2 but is not contained within either of the regions encompassed by reduced rules H1 and H2. As illustrated, this unique portion 614 comprises the set defined by port=[14, 18-20] Permit.

To understand how this is determined, recall that reduced rule L2 is represented by port=[14-20] Permit. Reduced rule H2 carves out the portion of L2 defined by port=[15-17] Permit, which is represented as overlap 616. This leaves only port=[14, 18-20] Permit as the non-overlap portion of the region encompassed by reduced rule L2. Correspondingly, this non-overlap portion (i.e. unique portion 614, the portion not common between the two models L_Permit_(BDD) and H_Permit_(BDD) under comparison) is added to Permit conflict ROBDD 600 b.

FIG. 6C illustrates a Permit conflict ROBDD 600 c which is identical to Permit conflict ROBDD 600 b with the exception of a newly added third rule, H3: port=[19-25] Permit. Reduced rule H3 consists of an overlap portion 628, which represents the set of conditions and actions that are contained in both reduced rules H3 and L2, and further consists of a unique portion 626, which represents the set of conditions and actions that are contained only in reduced rule H3. As was the case previously, note that the term ‘overlap’ is only applied between different models—because the reduced form of rules removes any overlap within a model itself, the term ‘overlap’ is not applied between constituent rules of the same model.

Conceptually, this could represent an error wherein an Li-model rule (i.e. L2) specified by a user intent was incorrectly rendered into TCAM or switch memory as two Hi-model rules (i.e. H2 and H3). There is no inherent fault with a single Li-model rule being represented as multiple Hi-model rules. Rather, the fault herein lies in the fact that the two corresponding Hi-model rules do not adequately capture the full extent of the set of packet configurations encompassed by the reduced Permit rule L2. Reduced rule H2 is too narrow in comparison to reduced rule L2, as discussed above with respect to FIG. 6B, and reduced rule H3 is both too narrow as well as improperly extended beyond the boundary of the region encompassed by reduced rule L2.

As was the case before, this error is detected by the construction of the conflict ROBDD 600 c, as L_Permit_(BDD) ⊕H_Permit_(BDD), where the results of this calculation are indicated by the shaded unique portion 624, representing the set of packet configurations and network actions that are contained within L_Permit_(BDD) but not H_Permit_(BDD), and the shaded unique portion 626, representing the set of packet configurations and network actions that are contained within H_Permit_(BDD) but not L_Permit_(BDD). In particular, unique portion 624 is contained only within reduced rule L2, and comprises the set defined by port=[14, 18] Permit, while unique portion 626 is contained only within reduced rule H3, and comprises the set defined by port=[21-25] Permit. Thus, Permit conflict ROBDD 600 c comprises the set defined by port=[14, 18, 21-25] Permit.

Reference is made above only to Permit conflict ROBDDs, although it is understood that conflict ROBDDs are generated for each action associated with a given model of network intents. For example, a complete analysis of the Li and Hi models mentioned above might entail using ROBDD Generator 530 to generate the eight ROBDDs L_Permit_(BDD), L_Permit_Log_(BDD), L_Deny_(BDD), and L_Deny_Log_(BDD), H_Permit_(BDD), H_Permit_Log_(BDD), H_Deny_(BDD), and H_Deny_Log_(BDD), and then using Equivalence Checker 540 to generate a Permit conflict ROBDD, Permit_Log conflict ROBDD, Deny conflict ROBDD, and Deny_Log conflict ROBDD.

In general, Equivalence Checker 540 generates action-specific conflict ROBDDs based on input models of network intent, or input ROBDDs from ROBDD Generator 530. As illustrated in FIG. 5, Equivalence Checker receives the input pairs (L_(BDD), H_(BDD)), (L_(BDD), C_(BDD)), (C_(BDD), H_(BDD)), although it is understood that these representations are for clarity purposes, and may be replaced with any of the action-specific ROBDDs discussed above. From these action-specific conflict ROBDDs, Equivalence Checker 540 may determine that there is no conflict between the inputs—that is, a given action-specific conflict ROBDD is empty. In the context of the examples of FIGS. 6A-6C, an empty conflict ROBDD would correspond to no shaded portions being present. In the case where this determination is made for the given action-specific conflict ROBDD, Equivalence Checker 540 might generate a corresponding action-specific “PASS” indication 544 that can be transmitted externally from formal analysis engine 502.

However, if Equivalence Checker 540 determines that there is a conflict between the inputs, and that a given action-specific conflict ROBDD is not empty, then Equivalence Checker 540 will not generate PASS indication 544, and can instead transmit the given action-specific conflict ROBDD 542 to a Conflict Rules Identifier 550, which identifies the specific conflict rules that are present. In some embodiments, an action-specific “PASS” indication 544 can be generated for every action-specific conflict ROBDD that is determined to be empty. In some embodiments, the “PASS” indication 544 might only be generated and/or transmitted once every action-specific conflict ROBDD has been determined to be empty.

In instances where one or more action-specific conflict ROBDDs are received, Conflict Rules Identifier 550 may also receive as input the flat listing of priority ordered reduced rules that are represented in each of the conflict ROBDDs 542. For example, if Conflict Rules Identifier 550 receives the Permit conflict ROBDD corresponding to L_Permit_(BDD) ⊕H_Permit_(BDD), the underlying flat listings of priority ordered reduced rules L_(i), H₁ used to generate L_Permit_(BDD) and H_Permit_(BDD) are also received as input.

The Conflict Rules Identifier 550 then identifies specific conflict rules from each listing of priority ordered rules and builds a listing of conflict rules 552. In order to do so, Conflict Rules Identifier 550 iterates through all of the rules contained within a given listing and calculates the intersection between the set of packet configurations and network actions that is encompassed by each given rule (or reduced rule), and the set that is encompassed by the action-specific conflict ROBDD. For example, assume that a list of j rules was used to generate L_Permit_(BDD). For each rule j, Conflict Rules Identifier 550 computes: (L_Permit_(BDD) ⊕H_Permit_(BDD))*L _(j) If this calculation equals zero, then the given rule L_(j) is not part of the conflict ROBDD and therefore is not a conflict rule. If, however, this calculation does not equal zero, then the given rule L_(j) is part of the Permit conflict ROBDD and therefore is a conflict rule that is added to the listing of conflict rules 552.

For example, in FIG. 6C, Permit conflict ROBDD 600 c consists of the shaded portions 624 and 626. Starting with the two rules L1, L2 used to generate L_Permit_(BDD), it can be calculated that: (L_Permit_(BDD) ⊕H_Permit_(BDD))*L1=0 Thus, rule L1 does not overlap with Permit conflict ROBDD 600 c and therefore is not a conflict rule. However, it can be calculated that: (L_Permit_(BDD) ⊕H_Permit_(BDD))*L2≠0 Meaning that rule L2 does overlap with Permit conflict ROBDD 600 c at overlap portion 624 and therefore is a conflict rule and is added to the listing of conflict rules 552.

The same form of computation can also be applied to the list of rules H1, H2, H3, used to generate H_Permit_(BDD). It can be calculated that: (L_Permit_(BDD) ⊕H_Permit_(BDD))*H1=0 Thus, rule H1 does not overlap with Permit conflict ROBDD 600 c and therefore is not a conflict rule. It can also be calculated that: (L_Permit_(BDD) ⊕H_Permit_(BDD))*H2=0 Thus, rule H2 does not overlap with Permit conflict ROBDD 600 c and therefore is not a conflict rule. Finally, it can be calculated that: (L_Permit_(BDD) ⊕H_Permit_(BDD))*H3≠0 Meaning that rule H3 does overlap with Permit conflict ROBDD 600 c at overlap portion 626 and therefore is a conflict rule and can be added to the listing of conflict rules 552. In the context of the present example, the complete listing of conflict rules 552 derived from Permit conflict ROBDD 600 c is {L2, H3}, as one or both of these rules have been configured or rendered incorrectly.

In some embodiments, one of the input models 506 may be treated as a reference or standard, meaning that the rules or reduced rules contained within that model are assumed to be correct. As such, Conflict Rules Identifier 550 only needs to compute the intersection of a given action-specific conflict ROBDD and the set of associated action-specific rules from the non-reference model. For example, the Li-model of user intents can be treated as a reference or standard, because it is directly derived from user inputs. The Hi-model, on the other hand, passes through several transformations before ultimately being rendered into a hardware form by a switch memory controller, and is therefore much more likely to be subject to error. Accordingly, the Conflict Rules Identifier 550 would only compute (L_Permit_(BDD) ⊕H_Permit_(BDD))*H _(j) for each of the rules j in the Hi-model, which can cut the required computation time roughly in half.

Additionally, as mentioned previously, Conflict Rules Identifier 550 need not calculate the intersection of the action-specific conflict ROBDD and the entirety of each rule, but instead, can use a priority-reduced form of each rule. In other words, this is the form in which the rule is represented within the ROBDD. For example, the priority reduced form of rule H2 is H1′H2, or the contribution of rule H2 minus the portion that is already captured by rule H1. The priority reduced form of rule H3 is (H1+H2)′H3, or the contribution of rule H3 minus the portion that is already captured by rules H1 or H2. The priority reduced form of rule H4 is (H1+H2+H3)′H4, or the contribution of rule H4 minus the portion that is already captured by rules H1 and H2 and H3.

As such, the calculation instead reduces to: (L_Permit_(BDD) ⊕H_Permit_(BDD))*(H1+ . . . +H _(j-1))′H _(j) for each reduced rule (or each reduced Permit rule) j that is contained in the Hi-model. While there are additional terms introduced in the equation above as compared to simply calculating (L_Permit_(BDD) ⊕H_Permit_(BDD))*H _(j), the priority-reduced form is in fact computationally more efficient. For each rule j, the priority-reduced form (H1+ . . . +H_(j-1))′H_(j) encompasses a smaller set of packet configurations and network actions, or encompasses an equally sized set, as compared to the non-reduced form H_(j). The smaller the set for which the intersection calculation is performed against the conflict ROBDD, the more efficient the computation. Accordingly, the priority-reduced form of the computation is, at worst, equivalent to the unmodified calculation, and in practice, is far faster.

The Conflict Rules Identifier 550 can then output a listing of conflict rules 552 (whether generated from both input models, or generated from only a single, non-reference input model) to a destination external to formal analysis engine 502. For example, the conflict rules 552 can be output to a user or network operator in order to better understand the specific reason that a conflict occurred between two models.

In some embodiments, a Back Annotator 560 can be disposed between Conflict Rules Identifier 550 and the external output. Back Annotator 560 can associate each given rule from the conflict rules listing 552 with the specific parent contract or other high-level intent that led to the given rule being generated. In this manner, not only is a formal equivalence failure explained to a user in terms of the specific rules that are in conflict, the equivalence failure is also explained to the user in terms of the high-level user action, configuration, or intent that was entered into the network and ultimately created the conflict rule. In this manner, a user can much more effectively address conflict rules, by adjusting or otherwise targeting them at their source or parent.

In some embodiments, the listing of conflict rules 552 may also be maintained and transmitted internal to formal analysis engine 502 to enable further network assurance analyses and operations such as event generation and counter-example generation.

The disclosure now turns to FIGS. 7 and 8, which illustrate example network devices and computing devices, such as switches, routers, load balancers, client devices, and so forth.

FIG. 7 illustrates an example network device 700 suitable for performing switching, routing, load balancing, and other networking operations. Network device 700 includes a central processing unit (CPU) 704, interfaces 702, and a bus 710 (e.g., a PCI bus). When acting under the control of appropriate software or firmware, the CPU 704 is responsible for executing packet management, error detection, and/or routing functions. The CPU 704 preferably accomplishes all these functions under the control of software including an operating system and any appropriate applications software. CPU 704 may include one or more processors 708, such as a processor from the INTEL X86 family of microprocessors. In some cases, processor 708 can be specially designed hardware for controlling the operations of network device 700. In some cases, a memory 706 (e.g., non-volatile RAM, ROM, etc.) also forms part of CPU 704. However, there are many different ways in which memory could be coupled to the system.

The interfaces 702 are typically provided as modular interface cards (sometimes referred to as “line cards”). Generally, they control the sending and receiving of data packets over the network and sometimes support other peripherals used with the network device 700. Among the interfaces that may be provided are Ethernet interfaces, frame relay interfaces, cable interfaces, DSL interfaces, token ring interfaces, and the like. In addition, various very high-speed interfaces may be provided such as fast token ring interfaces, wireless interfaces, Ethernet interfaces, Gigabit Ethernet interfaces, ATM interfaces, HSSI interfaces, POS interfaces, FDDI interfaces, WIFI interfaces, 3G/4G/5G cellular interfaces, CAN BUS, LoRA, and the like. Generally, these interfaces may include ports appropriate for communication with the appropriate media. In some cases, they may also include an independent processor and, in some instances, volatile RAM. The independent processors may control such communications intensive tasks as packet switching, media control, signal processing, crypto processing, and management. By providing separate processors for the communications intensive tasks, these interfaces allow the master microprocessor 604 to efficiently perform routing computations, network diagnostics, security functions, etc.

Although the system shown in FIG. 7 is one specific network device of the present invention, it is by no means the only network device architecture on which the present invention can be implemented. For example, an architecture having a single processor that handles communications as well as routing computations, etc., is often used. Further, other types of interfaces and media could also be used with the network device 700.

Regardless of the network device's configuration, it may employ one or more memories or memory modules (including memory 706) configured to store program instructions for the general-purpose network operations and mechanisms for roaming, route optimization and routing functions described herein. The program instructions may control the operation of an operating system and/or one or more applications, for example. The memory or memories may also be configured to store tables such as mobility binding, registration, and association tables, etc. Memory 706 could also hold various software containers and virtualized execution environments and data.

The network device 700 can also include an application-specific integrated circuit (ASIC), which can be configured to perform routing and/or switching operations. The ASIC can communicate with other components in the network device 700 via the bus 710, to exchange data and signals and coordinate various types of operations by the network device 700, such as routing, switching, and/or data storage operations, for example.

FIG. 8 illustrates a computing system architecture 800 wherein the components of the system are in electrical communication with each other using a connection 805, such as a bus. Exemplary system 800 includes a processing unit (CPU or processor) 810 and a system connection 805 that couples various system components including the system memory 815, such as read only memory (ROM) 820 and random access memory (RAM) 825, to the processor 810. The system 800 can include a cache of high-speed memory connected directly with, in close proximity to, or integrated as part of the processor 810. The system 800 can copy data from the memory 815 and/or the storage device 830 to the cache 812 for quick access by the processor 810. In this way, the cache can provide a performance boost that avoids processor 810 delays while waiting for data. These and other modules can control or be configured to control the processor 810 to perform various actions. Other system memory 815 may be available for use as well. The memory 815 can include multiple different types of memory with different performance characteristics. The processor 810 can include any general purpose processor and a hardware or software service, such as service 1 832, service 2 834, and service 3 836 stored in storage device 830, configured to control the processor 810 as well as a special-purpose processor where software instructions are incorporated into the actual processor design. The processor 810 may be a completely self-contained computing system, containing multiple cores or processors, a bus, memory controller, cache, etc. A multi-core processor may be symmetric or asymmetric.

To enable user interaction with the computing device 800, an input device 845 can represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech and so forth. An output device 835 can also be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multimodal systems can enable a user to provide multiple types of input to communicate with the computing device 800. The communications interface 840 can generally govern and manage the user input and system output. There is no restriction on operating on any particular hardware arrangement and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.

Storage device 830 is a non-volatile memory and can be a hard disk or other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, random access memories (RAMs) 825, read only memory (ROM) 820, and hybrids thereof.

The storage device 830 can include services 832, 834, 836 for controlling the processor 810. Other hardware or software modules are contemplated. The storage device 830 can be connected to the system connection 805. In one aspect, a hardware module that performs a particular function can include the software component stored in a computer-readable medium in connection with the necessary hardware components, such as the processor 810, connection 805, output device 835, and so forth, to carry out the function.

For clarity of explanation, in some instances the present technology may be presented as including individual functional blocks including functional blocks comprising devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software.

In some embodiments the computer-readable storage devices, mediums, and memories can include a cable or wireless signal containing a bit stream and the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implemented using computer-executable instructions that are stored or otherwise available from computer readable media. Such instructions can comprise, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Portions of computer resources used can be accessible over a network. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that may be used to store instructions, information used, and/or information created during methods according to described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprise hardware, firmware and/or software, and can take any of a variety of form factors. Typical examples of such form factors include laptops, smart phones, small form factor personal computers, personal digital assistants, rackmount devices, standalone devices, and so on. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functions described in these disclosures.

Although a variety of examples and other information was used to explain aspects within the scope of the appended claims, no limitation of the claims should be implied based on particular features or arrangements in such examples, as one of ordinary skill would be able to use these examples to derive a wide variety of implementations. Further and although some subject matter may have been described in language specific to examples of structural features and/or method steps, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to these described features or acts. For example, such functionality can be distributed differently or performed in components other than those identified herein. Rather, the described features and steps are disclosed as examples of components of systems and methods within the scope of the appended claims.

Claim language reciting “at least one of” refers to at least one of a set and indicates that one member of the set or multiple members of the set satisfy the claim. For example, claim language reciting “at least one of A and B” means A, B, or A and B. 

What is claimed is:
 1. A method comprising: obtaining, via one or more processors, a plurality of models of network intents; analyzing, via the one or more processors, the plurality of models to yield a result; when the result indicates a conflict, performing a conflict rule calculation to determine whether one or more rules is a conflict rule; and when the one or more rules is the conflict rule, generating a listing with the conflict rule and/or generating a notification with the conflict rule; wherein, determining whether the one or more rules is the conflict rule includes calculating an intersection, and the one or more rules is the conflict rule if the intersection is non-zero.
 2. The method of claim 1, wherein the intersection includes a logical exclusive disjunction that is a Reduced Ordered Binary Decision Diagram (ROBDD).
 3. The method of claim 1, wherein the plurality of models includes a reference model and a model under test.
 4. The method of claim 1, further comprising: performing back annotation to identify a contract or fabric-wide user intent from which the conflict rule was derived.
 5. The method of claim 1, wherein one or more of the plurality of models is a Reduced Ordered Binary Decision Diagram (ROBDD).
 6. The method of claim 5, wherein one or more of the plurality of models is specific to network intents corresponding to a Permit action, Permit_Log action, Deny action, or Deny_Log action.
 7. A system comprising: one or more processors; and at least one computer-readable storage medium having stored therein instructions which, when executed by the one or more processors, cause the system to: obtain a plurality of models of network intents; analyze the plurality of models to yield a result; when the result indicates a conflict, perform a conflict rule calculation to determine whether one or more rules is a conflict rule; and when the one or more rules is the conflict rule, generate a listing with the conflict rule and/or generate a notification with the conflict rule; wherein, determining whether the one or more rules is the conflict rule includes calculating an intersection, and the one or more rules is the conflict rule if the intersection is non-zero.
 8. The system of claim 7, wherein the plurality of models includes a reference model and a model under test.
 9. The system of claim 7, wherein the instructions further cause the system to perform back annotation to identify a contract or fabric-wide user intent from which the conflict rule was derived.
 10. The system of claim 7, wherein one or more of the plurality of models is a Reduced Ordered Binary Decision Diagram (ROBDD).
 11. The system of claim 7, wherein one or more of the plurality of models is specific to network intents corresponding to a Permit action, a Permit_Log action, a Deny action, or a Deny_Log action.
 12. A non-transitory computer-readable storage medium comprising: instructions stored therein which, when executed by one or more processors, cause the one or more processors to: obtain a plurality of models of network intents, analyze the plurality of models to yield a result, when the result indicates a conflict, perform a conflict rule calculation to determine whether one or more rules is a conflict rule, and when the one or more rules is the conflict rule, generate a listing with the conflict rule and/or generate a notification with the conflict rule; wherein, determining whether the one or more rules is the conflict rule includes calculating art intersection, and the one or more rules is the conflict rule if the intersection is non-zero.
 13. The non-transitory computer-readable storage medium of claim 12, wherein the intersection includes a logical exclusive disjunction that is a Reduced Ordered Binary Decision Diagram (ROBDD).
 14. The non-transitory computer-readable storage medium of claim 12, wherein the plurality of models includes a reference model and a model under test.
 15. The non-transitory computer-readable storage medium of claim 12, wherein the instructions further cause the one or more processors to perform back annotation to identify a contract or fabric-wide user intent from which the conflict rule was derived.
 16. The non-transitory computer-readable storage medium of claim 12, wherein one or more of the plurality of models is a Reduced Ordered Binary Decision Diagram (ROBDD).
 17. The non-transitory computer-readable storage medium of claim 12, wherein one or more of the plurality of models is specific to network intents corresponding to a Permit action, a Permit_Log action, a Deny action, or a Deny_Log action. 